The C++Builder 2006 personality included in this release of Borland Developer Studio 2006 is provided to you as a Technology Preview. We recognize the importance of a high quality C/C++ personality, and consider this Preview as the first step in providing that without delaying delivery of the rest of the studio to you. Borland plans to quickly follow this preview up with a free update by or before December 31st, 2005, downloadable from http://www.borland.com/downloads . This will update your Borland Developer Studio installation to the complete C++Builder 2006 functionality.
NOTE: The English version of BDS 2006 updates Internet Explorer with the English version of Internet Explorer 6.0 SP1. If you are running a localized operating system, run Windows Update to ensure that you get the proper localized version of Internet Explore
The bootstrap utility detects whether the following BDS 2006 pre-requisites are installed on your system:
If you install BDS 2006 using the installation launcher (install.exe in the root directory on Disk 1), the bootstrap utility runs automatically.
However, if you install BDS 2006 using setup.exe in the "Install" directory on Disk 1, the bootstrap utility is bypassed. Borland recommends that you run the bootstrap utility before running setup.exe. Run prereqs.exe in the "Install" directory on Disk 1.
If the utility does not find the pre-requisite software on your system, it prompts you to install the software. Reply yes to the prompts to install the software required for BDS 2006 to function properly. If you reply no, the BDS 2006 installation will not continue if any of the pre- requisites are not found.
For StarTeam to function property, you will need to install VJ# hotfix. This is not installed as part of the prereqs.exe boostrap. It is available in the Info\StarTeam Hotfix folder in Disk 1 of the product.
If you install Microsoft .NET Framework v1.1 SP1 using the bootstrap utility, you will be prompted to reboot the machine after Microsoft .NET Framework v1.1 SP1 installation is complete. You can click No to the prompt and reboot after all installations are complete.
The product can be installed by any licensed user with Administrator privileges, and is immediately available to all licensed users of the same machine. It is also available to any licensed users you may add later.
You will be prompted to reboot your system at the end of the BDS 2006 installation if you have chosen to install Internet Explorer 6.0 SP1 from the bootstrap utility (prereqs.exe) or Microsoft .NET Framework v1.1 SP1 or MDAC 2.8 from the BDS 2006 setup.
If the drive containing the folder specified in your TEMP environment variable is low on space, the Installer may halt with an error message noting the shortage. If this occurs, you'll need to assign your TEMP variable to a folder on a drive with more disk space, then rerun the installation.
Duplicate copies of assemblies installed in the GAC are provided in the <CommonFilesFolder>\Borland Shared\BDS\Shared Assemblies\4.0 directory. If C:\ is your Windows drive, the default <CommonFilesFolder> is C:\Program Files\Common Files\.
The assemblies in the GAC can be used to test deployment. The duplicate copy of the assemblies in the above mentioned directory can be used for development purposes. You can also use the redistributable installer for deployment purposes. It is located on Disk 4.
BDS 2006 stores assembly and Tool Palette configuration information in the file ApplicationSettings.xml, located in the user's home directory at "Documents and Settings\<username>\Local Settings\Application Data\Borland\BDS\4.0."
This file is not deleted during an uninstall and might cause assembly version errors in the IDE if you install another edition of BDS 2006 (for example, Enterprise or Architect) on the same machine. To avoid this problem, delete ApplicationSettings.xml BEFORE installing another product edition.
Setup will generate BdpDataSources.xml and bdpConnections.xml depending on the providers you choose during installation. At the end of the installation, setup will prompt you to overwrite or merge the bdpConnections.xml file if it exists in the destination directory. If you choose No at this prompt, the existing bdpConnections.xml file will be merged with the file being installed. If you choose Yes at the prompt, setup will replace the existing bdpConnections.xml file with the new file. By default, the bdpConnections.xml file is located at C:\Program Files\Borland\BDS\4.0\Bin.
Additional C++ demos are available in the Demos folder in Disk 4 of the product.
IMPORTANT: The C++Builder 2006 personality included in this release of Borland Developer Studio 2006 is provided to you as a Technology Preview. We recognize the importance of a high quality C/C++ personality, and consider this Preview as the first step in providing that without delaying delivery of the rest of the studio to you. Borland plans to quickly follow this preview up with a free update by or before December 31st, 2005, downloadable from http://www.borland.com/downloads . This will update your Borland Developer Studio installation to the complete C++Builder 2006 functionality.
Note: Silent installation is not supported for maintenance installations (if you are using the Modify option in Control Panel -> Add/Remove Programs).
To run a silent installation (install from a command line without the use of a GUI wizard), change to the System32 directory, and type the following in a command window:
<System32Folder>\msiexec.exe /I <.msi file> {/L*v "<log file>} {/qn | /qr | /qb} {PROPERTY1="value1", PROPERTY2="value2", ...} where
The following properties are supported by the Borland Developer Studio 2006 setup program:
Pass in a "1" to install the product, or put in an empty string ("") if you do not want to install it. If you don't pass in one of these properties, msi will launch the third-party setup scripts if the products are not already installed.
Pass "1" to install the personality, "" if you do not want to install it. By default all personalities are installed.
Pass "1" to associate the file extensions, "" to not associate. By default all file types that belong to the selected personalities will be associated with BDS.
ASSOC_DELPHIDOTNET will associate files of extension : pas, dpr, dpk, nfm
ASSOC_DELPHIWIN32 will associate files of extension : pas, dpr, dpk, dpkw, dfm, rc
ASSOC_CSHARP will associate files of extension : cs
ASSOC_BCB will associate files of extension : cpp, hpp, h, bpr, bpk, bpf, rc ASSOC_ASPDOTNET will associate files of extension : aspx, ascx, ashx, asax, asmx, bdsdeploy ASSOC_BDS will associate files of extension : bdsgroup, bdsproj
msiexec.exe /I "C:\setup\BDS2006.msi" /L*v "C:\temp\install.log" /qn DEBUG_MODE=ON INSTALLDIR="C:\Borland\BDS\4.0" BSBDE="C:\BorShared\BDE" INSTALL_NUNIT=1 INSTALL_RAVE="" INDY_VER=Indy10 CSHARP_PERSONALITY=""
To run a silent uninstallation (un-install from a command line without the use of a GUI wizard), type the following in a command window:
msiexec /x "<msi file>" {/L*v "log file"} {/qn | /qb | /qr} (or) if you don't have the .msi file, use the following syntax:
msiexec /x {7ED5371F-F4EA-48F9-B8F7-C8777AD9DF69} {/L*v "log file"} {/qn | /qb | /qr}
MSI Command-line Reference:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/command_line_options.asp
Once the product is installed, you can add optional products, add/remove personalities and/or add/remove features. Use the Control Panel | Add/Remove Programs command, select the "Modify" button, and then choose personalities/features that you want to add or remove.
The feature selection dialog that you see in maintenance mode is different from the one that is displayed during initial installation. During initial installation, only the features that are part of the selected personalities will be displayed in the feature selection dialog. But in maintenance mode, all features will be displayed in the dialog.
For example, if you initially installed only the Delphi.NET personality, when you use the Modify command to include the "Delphi Win32" personality, you will see all of the Delphi Win32 features in the feature selection tree disabled by default. You have to select all of the Delphi Win32 features that you want to install and then click Next to continue with installation.
Note that if you select features that are not part of the selected personality, those features will not be installed even though you selected them in the feature selection dialog. For example, if you installed Delphi Win32 and C++Builder with all features selected during initial installation, and then you use the Modify command to remove C++Builder, the feature selection dialog will show all of the C++Builder features such as Corba and CodeGuard enabled by default. This is because these features are currently installed on your system. But when you uncheck the C++Builder personality while you were using the Modify command to un-install, all of those C++Builder features will be removed (even though it looks like they are enabled by default).
Required for CaliberRM integration in Borland Developer Studio. This option enables CaliberRM users to add, remove, and update requirements for software projects within the Borland Developer Studio IDE and to create links between CaliberRM requirement specification and code.
Provides grid, reporting, charting, data, user-interface, and e-Commerce components for .NET and ASP.NET.
This option provides you with a .NET obfuscation tool that assists in protecting intellectual property by making it difficult to reverse engineer managed code applications and assemblies.
Rave Reports offers a powerful suite of Win32 and .NET components that simplify the task of creating professional reports.
A unit-testing framework for all .NET languages that takes advantage of many .NET language features, such as custom attributes and other reflection-related capabilities.
Microsoft Data Access Components (MDAC) 2.8 SP1 contains core Data Access components such as the Microsoft SQL Server™ OLE DB provider and ODBC driver. This redistributable installer for the MDAC 2.8 SP1 release installs the same Data Access components as Microsoft Windows XP SP2. This release does not include Microsoft Jet, the Microsoft Jet OLE DB Provider or ODBC driver, the Desktop Database ODBC Drivers, or the Visual FoxPro ODBC Driver.
Operating Systems Supported by MDAC 2.8: Windows 2000; Windows 98; Windows ME; Windows NT. For details, please visit http://www.microsoft.com/downloads/details.aspx?familyid=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&displaylang=en
Note: Read the WARNING at the end of this file before editing your system registry.
If you have BDE installed from any earlier version of BDS or C++Builder Architect or Enterprise Edition that co-exists with BDS Architect or Enterprise Editions, Borland strongly recommends that you perform a back up of the idapi32.cfg file in your BDE directory (by default C:\Program Files\Common Files\Borland Shared\BDE) before uninstalling BDS. The BDS 2006 uninstallation removes some BDE files including idapi32.cfg and this causes all pre- configured BDE aliases to be removed after uninstallation. If you have performed a back up of idapi32.cfg, then you can restore the BDE aliases by renaming the back up copy to idapi32.cfg after BDS 2006 uninstallation. You may also have to repair the earlier version of the BDS 2006 or C++Builder product by using the Add/Remove Programs command to restore the other missing BDE files.
To uninstall the product, the Administrator who initially installed the product must open the Control Panel, select Add or Remove Programs, select Borland BDS 2006 Architect Edition and click the Remove button. After uninstalling, in order to remove user-specific data from the Windows registry, all non- Administrator users of the product must log in and delete the following registry key:
HKEY_CURRENT_USER\Software\Borland\BDS\4.0
WARNING: Registry editing is performed at your own risk. This document and other documentation that accompanies this product describe how to edit your Windows registry. In most cases, Borland recommends that you use the Microsoft Regedit tool to perform editing. Whatever tool you use, however, you should, before making any changes, make backups of your registry and thoroughly familiarize yourself with the editing tool and the registry editing process. The registry is a critical component of your operating system, and any mistakes you make while editing it can cause your machine to stop functioning.
Copyright (c) 2005 Borland Software Corporation.
All rights reserved.